.
Warning tells you that your source
includes some problematic parts, that can lead to problems with several
browsers.
It can be suppressed using .
Error indicates that there is something
wrong with your html-source. No output is written.
Fatal error tells you that something
terrible has happened and there is no way to continue the conversion.
No output is written.
Note: I've already started to collect the messages, but
this list is not yet complete.
The project-file specified could not been open. This indicates
no problem, if you specified a project-file using
the first time; it will be created automatically after the
html-object has successfully been processed.
The data found in the project file are not of the required
form. Most likely, the file-format-version is outdated.
Remove the old file, will create a new one next time it
is invoked.
There are still characters to be read from input, but the file
already ends; tells you what it still expects to come.
An input file could not been opened. A more detailed message that tells
you why is displayed, too.
A keyword defined with the special attribute HSC.CLICK-HERE
has been found within the text inside an anchor specification.
Ok, now again in english: you used some term like "Click here" inside
the text describing a link. This is very clumsy and should be avoided;
see Composing
Good HTML for details.
You refered to an unknown tag or macro.
A tag that is expected to occure only once appeared at least twice.
Remove all unneccessary occurences of the tag.
You called a end-tag without using the corresponding start-tag
before.
A end-tag appeard where a different end-tag was expected to
appear before. Example: instead of
<$SOURCE PRE>
bold and italic
you should write
<$SOURCE PRE>
bold and italic
A tag that is required for every document is missing.
You called an start-tag, but didn't end it. Insert the required
end-tag.
You used an entity, that doesn't know. This can happen if you
made a typo, or the entity has not been defined within
hsc.prefs.
You referered to an attribute that doesn't exist at all.
A tag points to a local resource that doesn't exist.
You passed a value to an attribute, but did not embed it into single
or double quotes. This can lead to problems with older browsers.
An attribute referes to an attribute that has been defined, but no
value has been set for. Usually, you try to refer to an attribute
inside a macro, that no value has been passed to within the call
of the macro.
Some browser support the non-html-tag BLINK. It is used
to make text blinking, which annoys many users. Additionally, most
of them don't know how to configure their browser that it doesn't
blink, so you really should avoid it.
A "greater than" sign appeared inside the text. You should write
">" instead. This can also happen, if you made
an error calling a tag, and 's parser couln't recover.
You tried to set an enumerator to a value it doesn't support.
The tag was defined within some old html-version, but should
not be used any more (eg. LISTING).
This tag is no legal html-tag and is only supportet by special
browsers.
You defined a new attribute, but used an
option that is unknown.
An attribute that is required has not been set within the call
of a tag or macro.
Informs you that a special character (non-7-bit-ASCII) has been replaced
by it's corresponding entity.
You've called a shell-command using $exec and it returned a
value unequal to zero, which usually denotes an error while processing
the command. For error analysis, look at the output that the command
(hopefully) has made.
Icon-entities are (not-yet) widly supported.
Before you are allowed to use the first tag, the second tag has to
occure before. Example: INPUT may only occure
inside FORM.
A tag occures inside another tag that doesn't allowe this. For example,
you can't recursively use A inside A.
You tried to pass values to a end-tag or macro. If you need an attribute
for a end-macro only, you still have to define and pass it within the
start-macro; the end-macro will have access to all these attributes
and its values.
You redefined an alredy existing attribute. If this occures during
the definition of a new macro, you just tried to give two arguments the
same name.
You tried to use a simple tag as a container, for example /IMG
could not determine the size
of a link destination.
Somethings wrong with a or call.
A color value must fit the template `#rrggbb' or be one
of the values declared in the special attribute
HSC.COLOR-NAMES
defined in
This message should need no comment; anyway, read
Why Frames Suck
for more details.
See below.
These two messages point out that instead of (read the underscore (`_')
as a blank)
STRONG__important__/STRONG
you should better use
STRONGimportant/STRONG
It only affects the tags A, TITLE, headings and
physical/locigal styles.